|
Extreme programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development,〔 "Human Centred Technology Workshop 2005", 2005, PDF webpage: (Informatics-UK-report-cdrp585 ). 〕〔〔 it advocates frequent "releases" in short development cycles, which is intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted. Other elements of extreme programming include: programming in pairs or doing extensive code review, unit testing of all code, avoiding programming of features until they are actually needed, a flat management structure, simplicity and clarity in code, expecting changes in the customer's requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers.〔 "Design Patterns and Refactoring", University of Pennsylvania, 2003, webpage: (UPenn-Lectures-design-patterns ). 〕〔 "Extreme Programming" (USFCA-edu-601-lecture ). 〕〔 "Manifesto for Agile Software Development", Agile Alliance, 2001, webpage: (Manifesto-for-Agile-Software-Dev ) 〕 The methodology takes its name from the idea that the beneficial elements of traditional software engineering practices are taken to "extreme" levels. As an example, code reviews are considered a beneficial practice; taken to the extreme, code can be reviewed ''continuously'', i.e. the practice of pair programming. Critics have noted several potential drawbacks,〔 including problems with unstable requirements, no documented compromises of user conflicts, and a lack of an overall design specification or document. == History == Extreme Programming was created by Kent Beck during his work on the Chrysler Comprehensive Compensation System (C3) payroll project.〔 Beck became the C3 project leader in March 1996 and began to refine the development methodology used in the project and wrote a book on the methodology (in October 1999, ''Extreme Programming Explained'' was published).〔 "Extreme Programming", ''Computerworld'' (online), December 2001, webpage: (Computerworld-appdev-92 ). 〕 Chrysler cancelled the C3 project in February 2000, after seven years, when the company was acquired by Daimler-Benz. Although extreme programming itself is relatively new, many of its practices have been around for some time; the methodology, after all, takes "best practices" to extreme levels. For example, the "practice of test-first development, planning and writing tests before each micro-increment" was used as early as NASA's Project Mercury, in the early 1960s . To shorten the total development time, some formal test documents (such as for acceptance testing) have been developed in parallel (or shortly before) the software is ready for testing. A NASA independent test group can write the test procedures, based on formal requirements and logical limits, before the software has been written and integrated with the hardware. In XP, this concept is taken to the extreme level by writing automated tests (perhaps inside of software modules) which validate the operation of even small sections of software coding, rather than only testing the larger features. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Extreme programming」の詳細全文を読む スポンサード リンク
|